home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
s2a150.zip
/
S2ASETUP.DOC
< prev
next >
Wrap
Text File
|
1992-01-23
|
5KB
|
115 lines
┌──────────────────────┬───────────────────────────────────────┬────────┐
│ Send·2·ALL v1.50 │ Setup program for S2A and S2AMaint │ M ▀▀▄ │
│ Copyright (C) 1992 ├───────────────────────────────────────┤ ▄▄ █ │
│ by │ Maelstrom Online Services 1:117/351 │ ████ │
│ Kit Cragin │ Node 1 ■ (409)696-8722 USR HST Dual │ █ ▀▀ │
│ Maelstrom Software │ Node 2 ■ (409)764-6516 12/24MNP5 │ ▀▄▄ S │
└──────────────────────┴───────────────────────────────────────┴────────┘
USING THE PROGRAM (Read HELLO.!!! then S2A.DOC first!)
─────────────────────────────────────────────────────────────────────────
When you enter the program for the first time, it prompts you for the
config file that you wish to edit. If you are a 1 line BBS just hit
<enter>. If you are multinode then change the default to CONFIG.1 and
run the program again for each CONFIG.n file (where n is the LINE #).
You can also start the setup by typing:
S2ASETUP <configfile> <- This loads or creates the specified file
Note that newly created config files have defaults which correspond to
the EXHEADER.ANS file. You can edit EXHEADER.ANS with TheDraw or other
ansi editor, and change the defaults in the config file as you see
fit.
When you enter the setup main menu, go into each option and edit the
appropriate fields. Note that you must press <F10> for each set of
fields to save changes. Otherwise hit <ESC> to discard changes.
EDITING THE FIELDS
─────────────────────────────────────────────────────────────────────────
■ REGISTRATION DATA ── fill out your name and BBS name exactly as
you wish it to appear (case sensitive).
■ Leave registration code as `0' unless you have received your regis-
tration code. In that case enter it in the appropriate field.
■ FILENAMES & PATHS ── Fill in the paths/filenames of each field.
Note that fields 2 through 5 REQUIRE FULL PATH and FILENAME.
■ The last field asks for the path and filename of the drop file you
wish to use. Enter
<drive>:\<path>\DORINFO1.DEF
or
<drive>:\<path>\DOOR.SYS.
■ If you use DORINFO.DEF or DORINFO2.DEF or something like that, try
entering this here and seeing if S2A will run. Otherwise create a
DOOR.SYS or DORINFO1.DEF file.
■ LOCATIONS & COLORS ── Edit the color and position of each output
field to match with whatever header file you entered in FILENAMES
AND PATHS. Note that the text area must have at least 6 columns
and 1 row.
■ BULLETIN PARAMETERS ── Edit the bulletin parameters to taste. Most
of these are self explanatory but I will mention a few here:
■ GENERATE ON EXIT ── Answer YES if you wish new bulletin output
files to be generated immediately after a change has occurred.
This is recommended. There is a caution for multinode BBSes:
be careful about generating the file if a user is reading it!
■ CLEAR LINE METHOD ── Answer CLEAR if you wish to use an ANSI clear
line method or SPACE if you wish to overwrite with spaces.
If you select CLEAR, all text to the left of the cursor
position will be quickly cleared for the next bulletin.
SPACE is slower but is good for a `windowed' bulletin format.
■ BULLETIN PAUSE MODE ── Select BBS to use your BBS's built in text
file control codes (Best) or ANSI to use an ANSI pause sequence.
■ BBS WAIT CHARACTERS ── This is the sequence of characters that your
BBS interprets in a text file to mean `pause text' or `wait for
user to press enter'. Leave blank if your BBS does not have these
and answer ANSI to the field above.
■ PRE-TEXT CHARACTERS ── These are characters that you can save to the
bulletin output files before the bulletins are generated. This is
useful to put your BBS's `disable continue... prompt' or `stop
user from aborting text display' characters.
■ EXIT MESSAGES ── Edit the exit messages to your taste or leave the
defaults.
■ PREVIEW BULLETIN ── If you are a registered user, you can view what
an example bulletin looks like with the header file you have designed
and with all the fields filled in.
■ SAVE CONFIGURATION ── Does just that. Make sure that you have hit
<F10> for each set of fields so that the correct values are stored.
ADDITIONAL INFORMATION
─────────────────────────────────────────────────────────────────────────
See TIPS.S2A for customizing bulletins and other useful examples of
setups.
SUPPORT
─────────────────────────────────────────────────────────────────────────
I hope you find Send-2-ALL useful and enjoyable. If you have any com-
ments, suggestions, problems, or questions contact me by:
■ FIDO NETmail at 1:117/351
■ Calling Maelstrom at 409-696-8722 or 409-764-6516
■ Leaving a message in FIDO's DOORWARE or RA_UTIL echos
■ using USmail at PO Box 9078, College Station, TX 77842
── Kit